Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc2f027e610c75caf6f7c00f64090b7ce02b1a86bf01b6aa627e4f75f0393cff

Tx prefix hash: 478bb80124e42c1762ec09002bc0391575e1e6ae42b5c755152a8ad5a56635f6
Tx public key: 14d94fb9813f59fe0730ce430287ab6208a0a588b1089127d4fa4efc33a2f0b6
Timestamp: 1714507977 Timestamp [UCT]: 2024-04-30 20:12:57 Age [y:d:h:m:s]: 00:245:11:54:16
Block: 1012021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175716 RingCT/type: yes/0
Extra: 0114d94fb9813f59fe0730ce430287ab6208a0a588b1089127d4fa4efc33a2f0b60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a23ba94d5780ccb5eddd1979f6823c6fa13c81b1b6f7e8605c99698225cb14af 0.600000000000 1474423 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": 1012031, "vin": [ { "gen": { "height": 1012021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a23ba94d5780ccb5eddd1979f6823c6fa13c81b1b6f7e8605c99698225cb14af" } } ], "extra": [ 1, 20, 217, 79, 185, 129, 63, 89, 254, 7, 48, 206, 67, 2, 135, 171, 98, 8, 160, 165, 136, 177, 8, 145, 39, 212, 250, 78, 252, 51, 162, 240, 182, 2, 17, 0, 0, 0, 1, 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