Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52a95182cfd7e1636b1424d21fdd8ad1471b2f774548b9a2d83d0020480e0a09

Tx prefix hash: 25080f929bc396a970e9b984c567b2951d61e1759fc9b47ac6f320c70417a22c
Tx public key: ba76aa4139067a04c1bec4f042dc624f2b2c81fda111129b21d850948fbb8ef2
Timestamp: 1714254699 Timestamp [UCT]: 2024-04-27 21:51:39 Age [y:d:h:m:s]: 00:347:12:44:58
Block: 1009921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248437 RingCT/type: yes/0
Extra: 01ba76aa4139067a04c1bec4f042dc624f2b2c81fda111129b21d850948fbb8ef20211000000010011055b000000000000000000

1 output(s) for total of 0.607780000000 dcy

stealth address amount amount idx
00: 15915b1aa614837184e72d9b841e7bac1862c36b2689dad27913df1c8f627dc2 0.607780000000 1471727 of 0

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": 1009931, "vin": [ { "gen": { "height": 1009921 } } ], "vout": [ { "amount": 607780000, "target": { "key": "15915b1aa614837184e72d9b841e7bac1862c36b2689dad27913df1c8f627dc2" } } ], "extra": [ 1, 186, 118, 170, 65, 57, 6, 122, 4, 193, 190, 196, 240, 66, 220, 98, 79, 43, 44, 129, 253, 161, 17, 18, 155, 33, 216, 80, 148, 143, 187, 142, 242, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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