Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 651d2996ca5ce56217dec288a7332e7952581536c4027bc7f66b24e555d76ff1

Tx prefix hash: c863f54283fcbeabfa2197dd41b518c51635aefd4d55d663ea9ebd1b794beb3a
Tx public key: cddc12bdabbe422a9b3c2344038775d80c42004afb09f2b962e5e3db01c5166b
Timestamp: 1728734614 Timestamp [UCT]: 2024-10-12 12:03:34 Age [y:d:h:m:s]: 00:165:12:53:34
Block: 1129972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118072 RingCT/type: yes/0
Extra: 01cddc12bdabbe422a9b3c2344038775d80c42004afb09f2b962e5e3db01c5166b02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 337f7747d3b4bcd13107c1ff53abefd625fb8a9f7e44dbe887761f0b542228a5 0.600000000000 1612843 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": 1129982, "vin": [ { "gen": { "height": 1129972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "337f7747d3b4bcd13107c1ff53abefd625fb8a9f7e44dbe887761f0b542228a5" } } ], "extra": [ 1, 205, 220, 18, 189, 171, 190, 66, 42, 155, 60, 35, 68, 3, 135, 117, 216, 12, 66, 0, 74, 251, 9, 242, 185, 98, 229, 227, 219, 1, 197, 22, 107, 2, 17, 0, 0, 0, 5, 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