Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57e51a07be590c4b993b7a4c02f4dd54e781f2df0e3446b26cfad1f2db3b4338

Tx prefix hash: d87175666179c72cfde56d4e8e9a0d19ce055e292495b69cf91d166cb1b0d9bc
Tx public key: 158ff994f7e6d02e04febd93bc930f1e7e829fdfd16d2bd21af16cbaa3bc165a
Timestamp: 1732869626 Timestamp [UCT]: 2024-11-29 08:40:26 Age [y:d:h:m:s]: 00:126:02:16:16
Block: 1164154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89923 RingCT/type: yes/0
Extra: 01158ff994f7e6d02e04febd93bc930f1e7e829fdfd16d2bd21af16cbaa3bc165a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13afd167c385c810862d6f2318bff0bb7a7fae3b4c7cb758437e0f7caf8cfb86 0.600000000000 1649827 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": 1164164, "vin": [ { "gen": { "height": 1164154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13afd167c385c810862d6f2318bff0bb7a7fae3b4c7cb758437e0f7caf8cfb86" } } ], "extra": [ 1, 21, 143, 249, 148, 247, 230, 208, 46, 4, 254, 189, 147, 188, 147, 15, 30, 126, 130, 159, 223, 209, 109, 43, 210, 26, 241, 108, 186, 163, 188, 22, 90, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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