Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0bce77b17cfc590c6a3f007bb75649dcc275cb428fd4941f8d45da989db6de

Tx prefix hash: 1fb1a20103753a04dd82e4abe1f2f9c4791a655da63cc363a3cc12526a8352f1
Tx public key: 36c288ea7f3f97c74f2fbd4e74f62b367c818ef7882f9d3eb5857d93a93684e1
Timestamp: 1709127268 Timestamp [UCT]: 2024-02-28 13:34:28 Age [y:d:h:m:s]: 01:064:19:02:28
Block: 967421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307337 RingCT/type: yes/0
Extra: 0136c288ea7f3f97c74f2fbd4e74f62b367c818ef7882f9d3eb5857d93a93684e102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b21d9bdbc2de8589b3f8a2f6479d01fa86250f6169ccb886afd35a31ee8a759 0.600000000000 1427200 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": 967431, "vin": [ { "gen": { "height": 967421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b21d9bdbc2de8589b3f8a2f6479d01fa86250f6169ccb886afd35a31ee8a759" } } ], "extra": [ 1, 54, 194, 136, 234, 127, 63, 151, 199, 79, 47, 189, 78, 116, 246, 43, 54, 124, 129, 142, 247, 136, 47, 157, 62, 181, 133, 125, 147, 169, 54, 132, 225, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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