Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cac64299c2b82ba9922d68eea9a02e144c01be5691cdbaffaf2cf2920192ef9

Tx prefix hash: 64d1b6f5ae09deb5317af8dd82a8aa0472c7cb3164d1d67c4f55e662d118ce70
Tx public key: 5f34b20dc759fee47b1e08a13583ff25616ecc5ad69cd126fad20d7a12fda5b0
Timestamp: 1711970941 Timestamp [UCT]: 2024-04-01 11:29:01 Age [y:d:h:m:s]: 01:079:00:49:59
Block: 990957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317381 RingCT/type: yes/0
Extra: 015f34b20dc759fee47b1e08a13583ff25616ecc5ad69cd126fad20d7a12fda5b002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecb5387de3c941a6946cf2d27200a5c84d7d191568b4f87b0016ffac8522d4f9 0.600000000000 1451289 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": 990967, "vin": [ { "gen": { "height": 990957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecb5387de3c941a6946cf2d27200a5c84d7d191568b4f87b0016ffac8522d4f9" } } ], "extra": [ 1, 95, 52, 178, 13, 199, 89, 254, 228, 123, 30, 8, 161, 53, 131, 255, 37, 97, 110, 204, 90, 214, 156, 209, 38, 250, 210, 13, 122, 18, 253, 165, 176, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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