Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e1da8c4cc0d8f27c992aae1caa48804b81107e366cc0f40dbf443800f740ca2

Tx prefix hash: b5296a03b02a8359d23cf3b65cdae8728024974b4b1768751d3e98702aef4197
Tx public key: c9e1e6b47e3c4b4cac52481252bc5c8c672e914b408981d0b130ed23d1b43568
Timestamp: 1735191739 Timestamp [UCT]: 2024-12-26 05:42:19 Age [y:d:h:m:s]: 00:171:19:42:27
Block: 1183389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122527 RingCT/type: yes/0
Extra: 01c9e1e6b47e3c4b4cac52481252bc5c8c672e914b408981d0b130ed23d1b43568021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc0e5deba4a537cf2cd84cc0fe300183775beab90814b6238376540f398c2ade 0.600000000000 1669834 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": 1183399, "vin": [ { "gen": { "height": 1183389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc0e5deba4a537cf2cd84cc0fe300183775beab90814b6238376540f398c2ade" } } ], "extra": [ 1, 201, 225, 230, 180, 126, 60, 75, 76, 172, 82, 72, 18, 82, 188, 92, 140, 103, 46, 145, 75, 64, 137, 129, 208, 177, 48, 237, 35, 209, 180, 53, 104, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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