Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 942e897a09c7e12f775a7b255b91e5095b47f321ade00586cfab6fb2a2148bb9

Tx prefix hash: 03153881bc7852805b9b9ffbd428d74b8229767c59d4b686528dabc75e05968a
Tx public key: a8c80fa0f674797e89f76a461a4503e7a662760bc9f84e7704a304dc1a965873
Timestamp: 1708435475 Timestamp [UCT]: 2024-02-20 13:24:35 Age [y:d:h:m:s]: 01:260:10:38:45
Block: 961676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444879 RingCT/type: yes/0
Extra: 01a8c80fa0f674797e89f76a461a4503e7a662760bc9f84e7704a304dc1a9658730211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea55d293ec927e0c98212d630adbb32e411e1c3c36c0d52b3eb3efd20c15479a 0.600000000000 1421287 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": 961686, "vin": [ { "gen": { "height": 961676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea55d293ec927e0c98212d630adbb32e411e1c3c36c0d52b3eb3efd20c15479a" } } ], "extra": [ 1, 168, 200, 15, 160, 246, 116, 121, 126, 137, 247, 106, 70, 26, 69, 3, 231, 166, 98, 118, 11, 201, 248, 78, 119, 4, 163, 4, 220, 26, 150, 88, 115, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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