Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2253711c268bb5b39d58d0430234e6660cbf75660645059509673fe89c491af

Tx prefix hash: 0f910ecfa3e66d5df36f28d9af10997d2b1ca1cb045168840df11c45077ba86a
Tx public key: d04564075e691812435e0b75b4b4dc236e78f8309078b9096d7b7ed260cceaef
Timestamp: 1578669370 Timestamp [UCT]: 2020-01-10 15:16:10 Age [y:d:h:m:s]: 05:024:05:14:02
Block: 42798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167213 RingCT/type: yes/0
Extra: 01d04564075e691812435e0b75b4b4dc236e78f8309078b9096d7b7ed260cceaef02110000000c4943cd9f000000000000000000

1 output(s) for total of 442.863581036000 dcy

stealth address amount amount idx
00: 3adccbe1dd2ca0e2bb81c931fcfbc3fbc3f1caff07f2c22b21be58198ad330a6 442.863581036000 77207 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": 42808, "vin": [ { "gen": { "height": 42798 } } ], "vout": [ { "amount": 442863581036, "target": { "key": "3adccbe1dd2ca0e2bb81c931fcfbc3fbc3f1caff07f2c22b21be58198ad330a6" } } ], "extra": [ 1, 208, 69, 100, 7, 94, 105, 24, 18, 67, 94, 11, 117, 180, 180, 220, 35, 110, 120, 248, 48, 144, 120, 185, 9, 109, 123, 126, 210, 96, 204, 234, 239, 2, 17, 0, 0, 0, 12, 73, 67, 205, 159, 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