Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee6d9e9d92ff7e51e440d8579fb39863893c64d78398155584862e5e2f6cb241

Tx prefix hash: d39c9a9b0918ae07959e286374e414bf692fc5a9f344b68d2c685054dc359c0d
Tx public key: 6f770efa3c37ba8d209ab7bba7709a9eb726229fd160ffd4e6c5a3933a78bd6c
Timestamp: 1710297412 Timestamp [UCT]: 2024-03-13 02:36:52 Age [y:d:h:m:s]: 01:021:23:17:14
Block: 977128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276669 RingCT/type: yes/0
Extra: 016f770efa3c37ba8d209ab7bba7709a9eb726229fd160ffd4e6c5a3933a78bd6c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbc9da6667df451f936167a20b9ed1d04c49aead0d98c2144e4f0c2e1a2baef 0.600000000000 1437129 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": 977138, "vin": [ { "gen": { "height": 977128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbc9da6667df451f936167a20b9ed1d04c49aead0d98c2144e4f0c2e1a2baef" } } ], "extra": [ 1, 111, 119, 14, 250, 60, 55, 186, 141, 32, 154, 183, 187, 167, 112, 154, 158, 183, 38, 34, 159, 209, 96, 255, 212, 230, 197, 163, 147, 58, 120, 189, 108, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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