Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd71ef009ff4e59f972c0d026e6123339736e9f3ed201219c51b5071522f132b

Tx prefix hash: 5ca8c55d8b10f01c1bcf1bd3147ce06516c5a0b8ab8f21d01759bf5f62c9949c
Tx public key: e6dfdf9017ef0eaabfcb7d28a47591d3464c553db6d9c8aa6c95d0dc4fed8596
Timestamp: 1725615264 Timestamp [UCT]: 2024-09-06 09:34:24 Age [y:d:h:m:s]: 00:083:18:41:31
Block: 1104114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59906 RingCT/type: yes/0
Extra: 01e6dfdf9017ef0eaabfcb7d28a47591d3464c553db6d9c8aa6c95d0dc4fed8596021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdd98ea06c0a18d24e1a997c3f00bbd264c6f55b941d8f9075737931d895524a 0.600000000000 1581185 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": 1104124, "vin": [ { "gen": { "height": 1104114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdd98ea06c0a18d24e1a997c3f00bbd264c6f55b941d8f9075737931d895524a" } } ], "extra": [ 1, 230, 223, 223, 144, 23, 239, 14, 170, 191, 203, 125, 40, 164, 117, 145, 211, 70, 76, 85, 61, 182, 217, 200, 170, 108, 149, 208, 220, 79, 237, 133, 150, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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