Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574b3c6972c1fa625accb19467bad0cf9fc2a85e119a6208a70ea53a60ffecdd

Tx prefix hash: ad79da07ce43c3835e6129c7c950972b7755df3ba7397f858081159b95509bbd
Tx public key: a32f105a5e26eec7c1da51f4493ced3c59dc12fb8e2873149ce56d7d7b1a9c76
Timestamp: 1734538224 Timestamp [UCT]: 2024-12-18 16:10:24 Age [y:d:h:m:s]: 00:101:14:56:47
Block: 1178000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72384 RingCT/type: yes/0
Extra: 01a32f105a5e26eec7c1da51f4493ced3c59dc12fb8e2873149ce56d7d7b1a9c760211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93236e4d38c765a7a0f48084e9b941f114924facb31c2c47274e00771b2688a7 0.600000000000 1664383 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": 1178010, "vin": [ { "gen": { "height": 1178000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93236e4d38c765a7a0f48084e9b941f114924facb31c2c47274e00771b2688a7" } } ], "extra": [ 1, 163, 47, 16, 90, 94, 38, 238, 199, 193, 218, 81, 244, 73, 60, 237, 60, 89, 220, 18, 251, 142, 40, 115, 20, 156, 229, 109, 125, 123, 26, 156, 118, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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