Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85bd8bc0c6d916f75b74682efd9c8393e34dd45dc5be92813ce5e27762baf4b4

Tx prefix hash: 523f3c38d229ef85332b1d77bf2c22f5f88bda3999c713d691960abd2533f9ad
Tx public key: 45c40605e2ee3037888a6d5c294a9ccc1baa400fab73fd690816077cc66af9e3
Timestamp: 1705674597 Timestamp [UCT]: 2024-01-19 14:29:57 Age [y:d:h:m:s]: 01:037:15:08:17
Block: 938754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287969 RingCT/type: yes/0
Extra: 0145c40605e2ee3037888a6d5c294a9ccc1baa400fab73fd690816077cc66af9e30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dae33b38fea21a45a4abcf543b3d059c17bcf503dbfac85279de40e804a4fee 0.600000000000 1396832 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": 938764, "vin": [ { "gen": { "height": 938754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dae33b38fea21a45a4abcf543b3d059c17bcf503dbfac85279de40e804a4fee" } } ], "extra": [ 1, 69, 196, 6, 5, 226, 238, 48, 55, 136, 138, 109, 92, 41, 74, 156, 204, 27, 170, 64, 15, 171, 115, 253, 105, 8, 22, 7, 124, 198, 106, 249, 227, 2, 17, 0, 0, 0, 1, 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