Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 97e2336720dd95284db1a60c9c6a7a8755ca090ef7b9b83d6e6934131bcd33af

Tx prefix hash: 2970e0929027743b7a7094607bd8e078aad9ae18eb8ac7efd4931ee5b91c2112
Tx public key: 66bb664ca5314ece3a232243573e2a7021c8f74bc4e6e916a6d2c81455da91d9
Timestamp: 1709211451 Timestamp [UCT]: 2024-02-29 12:57:31 Age [y:d:h:m:s]: 01:040:16:38:23
Block: 968122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290090 RingCT/type: yes/0
Extra: 0166bb664ca5314ece3a232243573e2a7021c8f74bc4e6e916a6d2c81455da91d9021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f8f1cc39a0818fa0a05c4a3189b0fc1f8637c6911c61f00db29514c760fa1ea 0.600000000000 1427921 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 968132, "vin": [ { "gen": { "height": 968122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f8f1cc39a0818fa0a05c4a3189b0fc1f8637c6911c61f00db29514c760fa1ea" } } ], "extra": [ 1, 102, 187, 102, 76, 165, 49, 78, 206, 58, 35, 34, 67, 87, 62, 42, 112, 33, 200, 247, 75, 196, 230, 233, 22, 166, 210, 200, 20, 85, 218, 145, 217, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8