Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05853df2e61c9d6bbc3fb6cb4e1e8b3f2bdae330ba2d1d0ee834b9cb429882a2

Tx prefix hash: d88860271e9d00ac079b6ff5850f4734aa9ef1d7fff8fac476024c3bdabca3cb
Tx public key: 62735101a6ed170df1e89889994e5d54cbf2b97aca80596f3ea8dc85c6d6789c
Timestamp: 1700081437 Timestamp [UCT]: 2023-11-15 20:50:37 Age [y:d:h:m:s]: 01:139:22:46:19
Block: 892419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361190 RingCT/type: yes/0
Extra: 0162735101a6ed170df1e89889994e5d54cbf2b97aca80596f3ea8dc85c6d6789c02110000000633af99f4000000000000000000

1 output(s) for total of 0.677712329000 dcy

stealth address amount amount idx
00: 569f3c96868abd4ad48daad0ff9f38244c1a9454381fb447ed805632914e6f23 0.677712329000 1348538 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": 892429, "vin": [ { "gen": { "height": 892419 } } ], "vout": [ { "amount": 677712329, "target": { "key": "569f3c96868abd4ad48daad0ff9f38244c1a9454381fb447ed805632914e6f23" } } ], "extra": [ 1, 98, 115, 81, 1, 166, 237, 23, 13, 241, 232, 152, 137, 153, 78, 93, 84, 203, 242, 185, 122, 202, 128, 89, 111, 62, 168, 220, 133, 198, 214, 120, 156, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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