Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5da16c394e179ac0a18c75dd5183bd59dcb7c20bb2367c8acfa70b26a6834df6

Tx prefix hash: 8b53415d14520c468f19f0e45b0b8be320ba2a4f33ab0ba910cadecb54a8df2a
Tx public key: 28933e24c877a7f72f48b696c702e7f26f221673352bf2a6cf8ba2d2c0410d30
Timestamp: 1762840415 Timestamp [UCT]: 2025-11-11 05:53:35 Age [y:d:h:m:s]: 00:082:10:36:20
Block: 1409593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58855 RingCT/type: yes/0
Extra: 0128933e24c877a7f72f48b696c702e7f26f221673352bf2a6cf8ba2d2c0410d30021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b3bb7e928815c1d114aa6e68b47ee62d3c78abaef089f4d2a165f492b06375c 0.600000000000 1898040 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": 1409603, "vin": [ { "gen": { "height": 1409593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b3bb7e928815c1d114aa6e68b47ee62d3c78abaef089f4d2a165f492b06375c" } } ], "extra": [ 1, 40, 147, 62, 36, 200, 119, 167, 247, 47, 72, 182, 150, 199, 2, 231, 242, 111, 34, 22, 115, 53, 43, 242, 166, 207, 139, 162, 210, 192, 65, 13, 48, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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