Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392980e4122db0fbc0c281e525ba64e541a10dd8488060233af9031dab83a0b6

Tx prefix hash: 2f800f698c39ae3a87dc741ee3338fa030f450e639187b9e9a34029595c008ba
Tx public key: c68538ffc0aab1c12559dc1c3f3f076799edb39749fbe01fdcfbe7c627684f4b
Timestamp: 1685992843 Timestamp [UCT]: 2023-06-05 19:20:43 Age [y:d:h:m:s]: 01:220:21:37:36
Block: 775869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419283 RingCT/type: yes/0
Extra: 01c68538ffc0aab1c12559dc1c3f3f076799edb39749fbe01fdcfbe7c627684f4b0211000000014b8f5122000000000000000000

1 output(s) for total of 1.649013039000 dcy

stealth address amount amount idx
00: b7394b08deed89253e21041da72fb7c4cdfcb2cb4330f9b2f9485fb0b465e7f0 1.649013039000 1225398 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": 775879, "vin": [ { "gen": { "height": 775869 } } ], "vout": [ { "amount": 1649013039, "target": { "key": "b7394b08deed89253e21041da72fb7c4cdfcb2cb4330f9b2f9485fb0b465e7f0" } } ], "extra": [ 1, 198, 133, 56, 255, 192, 170, 177, 193, 37, 89, 220, 28, 63, 63, 7, 103, 153, 237, 179, 151, 73, 251, 224, 31, 220, 251, 231, 198, 39, 104, 79, 75, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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