Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7529744f5de4afacd66323589d9a016b93f3f79bf50b73c5d4b67fa1abdafd83

Tx prefix hash: 70b50cea669d459fe3a96094e2f57f76551d0f5f6f194f32ed417c92955fdb85
Tx public key: 908aa02e89df03e7f79db6c86f8c5f85ea7c3767443d412180e1c61dc373f531
Timestamp: 1758265317 Timestamp [UCT]: 2025-09-19 07:01:57 Age [y:d:h:m:s]: 00:055:21:44:01
Block: 1371689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40023 RingCT/type: yes/0
Extra: 01908aa02e89df03e7f79db6c86f8c5f85ea7c3767443d412180e1c61dc373f531021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 848a51669468d60e2ba7b279e56d52b95fe3197776e06bb4702e2cc179091ab9 0.600000000000 1859766 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": 1371699, "vin": [ { "gen": { "height": 1371689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "848a51669468d60e2ba7b279e56d52b95fe3197776e06bb4702e2cc179091ab9" } } ], "extra": [ 1, 144, 138, 160, 46, 137, 223, 3, 231, 247, 157, 182, 200, 111, 140, 95, 133, 234, 124, 55, 103, 68, 61, 65, 33, 128, 225, 198, 29, 195, 115, 245, 49, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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