Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b3f21fc9aa9891e75f61476916f3fda8e1435d10e797d87b39e964933cc6f0

Tx prefix hash: d28fd40a2aa87b2592575fd0ed5e2944602ea5b7c75c7d014c701e42abb24240
Tx public key: 5ab787a6f9323eb1685ae85f017dc9de4fb526d8101f48f28ddbb7344c614c6c
Timestamp: 1697324301 Timestamp [UCT]: 2023-10-14 22:58:21 Age [y:d:h:m:s]: 02:028:03:40:10
Block: 869765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539740 RingCT/type: yes/0
Extra: 015ab787a6f9323eb1685ae85f017dc9de4fb526d8101f48f28ddbb7344c614c6c02110000000833af99f4000000000000000000

1 output(s) for total of 0.805577868000 dcy

stealth address amount amount idx
00: 69e310f442e6bb0a455b86c083eba8938557997220aa25a78c781d93e5f90943 0.805577868000 1324620 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": 869775, "vin": [ { "gen": { "height": 869765 } } ], "vout": [ { "amount": 805577868, "target": { "key": "69e310f442e6bb0a455b86c083eba8938557997220aa25a78c781d93e5f90943" } } ], "extra": [ 1, 90, 183, 135, 166, 249, 50, 62, 177, 104, 90, 232, 95, 1, 125, 201, 222, 79, 181, 38, 216, 16, 31, 72, 242, 141, 219, 183, 52, 76, 97, 76, 108, 2, 17, 0, 0, 0, 8, 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