Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d022f67341e0cdb9a1e42d3829eb03f02d1651f4073546ca7682656bbfaedc12

Tx prefix hash: a17c813383f8d4d9c62c67e89b1e27e6dc8c4ab43a3b7603f04057666eb502d0
Tx public key: 83aa6e89b90d9d5954828c590086ea2b4a84e45ee53335db40ae56d2045063c8
Timestamp: 1720713338 Timestamp [UCT]: 2024-07-11 15:55:38 Age [y:d:h:m:s]: 00:265:17:05:13
Block: 1063473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189824 RingCT/type: yes/0
Extra: 0183aa6e89b90d9d5954828c590086ea2b4a84e45ee53335db40ae56d2045063c802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 886e2be46add5e0117c39a4935278eb9e856a77374691cc5240c480c3843bf20 0.600000000000 1533988 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": 1063483, "vin": [ { "gen": { "height": 1063473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "886e2be46add5e0117c39a4935278eb9e856a77374691cc5240c480c3843bf20" } } ], "extra": [ 1, 131, 170, 110, 137, 185, 13, 157, 89, 84, 130, 140, 89, 0, 134, 234, 43, 74, 132, 228, 94, 229, 51, 53, 219, 64, 174, 86, 210, 4, 80, 99, 200, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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