Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e51b961d1c1dedfefe73310df7fc9b3933fe52db2ee059832072fe7ee3f35d2

Tx prefix hash: daa221543df263246194adfd649b1580aaed1359c25c9735395be7ef3a0d6398
Tx public key: 8ccdfe9c7e728d89f13a951ce75d14fae896d08d47f17b3c1350d3062e32eca8
Timestamp: 1711054402 Timestamp [UCT]: 2024-03-21 20:53:22 Age [y:d:h:m:s]: 00:361:13:08:44
Block: 983410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258498 RingCT/type: yes/0
Extra: 018ccdfe9c7e728d89f13a951ce75d14fae896d08d47f17b3c1350d3062e32eca802110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da91280e47387762fdec1b2adecbac39e0a4e9b365ae62f3b83cffd4c2849b3d 0.600000000000 1443541 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": 983420, "vin": [ { "gen": { "height": 983410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da91280e47387762fdec1b2adecbac39e0a4e9b365ae62f3b83cffd4c2849b3d" } } ], "extra": [ 1, 140, 205, 254, 156, 126, 114, 141, 137, 241, 58, 149, 28, 231, 93, 20, 250, 232, 150, 208, 141, 71, 241, 123, 60, 19, 80, 211, 6, 46, 50, 236, 168, 2, 17, 0, 0, 0, 8, 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