Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99df136a49587ad09fee6f194a1ced76cf40c06ea12d04b4da420b1a9baa66f3

Tx prefix hash: 434aa2dc7406b3b15165633f1d9711c2a2012be890dbb62c3167d1027efecde4
Tx public key: b8a016a294b2f220b7f112cf7580de83bc2c7d71588e9bfadb8d9ffc2a14793a
Timestamp: 1738467244 Timestamp [UCT]: 2025-02-02 03:34:04 Age [y:d:h:m:s]: 00:292:20:47:56
Block: 1210228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207079 RingCT/type: yes/0
Extra: 01b8a016a294b2f220b7f112cf7580de83bc2c7d71588e9bfadb8d9ffc2a14793a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efadd1bd4ed611bdf38c49d97e1c7f928a694ed5a42df571a139c3ec6df158af 0.600000000000 1696979 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": 1210238, "vin": [ { "gen": { "height": 1210228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efadd1bd4ed611bdf38c49d97e1c7f928a694ed5a42df571a139c3ec6df158af" } } ], "extra": [ 1, 184, 160, 22, 162, 148, 178, 242, 32, 183, 241, 18, 207, 117, 128, 222, 131, 188, 44, 125, 113, 88, 142, 155, 250, 219, 141, 159, 252, 42, 20, 121, 58, 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