Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e17fa163020c31316439e31738db1a21fa3669d2dae2d5209220eb846822037

Tx prefix hash: 05be399e50920bff6e392b09922bfcdd816103fba187bb839621dd1d2b7b1248
Tx public key: 6c562f139819cbdb1e0ab9a298b38c3337bab7507e62093c70e7cd6d8d2789cb
Timestamp: 1728291921 Timestamp [UCT]: 2024-10-07 09:05:21 Age [y:d:h:m:s]: 00:052:03:14:21
Block: 1126299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37250 RingCT/type: yes/0
Extra: 016c562f139819cbdb1e0ab9a298b38c3337bab7507e62093c70e7cd6d8d2789cb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c1026edc3e7782d5bc5fe83397e0a71e6502b58b11c2c7cb25a4c4bdac43814 0.600000000000 1609088 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": 1126309, "vin": [ { "gen": { "height": 1126299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c1026edc3e7782d5bc5fe83397e0a71e6502b58b11c2c7cb25a4c4bdac43814" } } ], "extra": [ 1, 108, 86, 47, 19, 152, 25, 203, 219, 30, 10, 185, 162, 152, 179, 140, 51, 55, 186, 183, 80, 126, 98, 9, 60, 112, 231, 205, 109, 141, 39, 137, 203, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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