Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73e0640fa41043e7791697c4fe922f49572f45d9267c3fa1296cbf1429b07906

Tx prefix hash: f482b0b4a927b3220d178a093e7c88e361978e55cfffbbb2830652a9ed41c24e
Tx public key: 889326b0afb3bb316854cbd2ba1a2a23fdb169e1e31b5a581caad42d23f19dac
Timestamp: 1702749855 Timestamp [UCT]: 2023-12-16 18:04:15 Age [y:d:h:m:s]: 01:100:19:10:28
Block: 914543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333159 RingCT/type: yes/0
Extra: 01889326b0afb3bb316854cbd2ba1a2a23fdb169e1e31b5a581caad42d23f19dac021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f90cdcc88e31f667b311b04455f9d437b5e14f8bfafc0ac285ef7edf633401 0.600000000000 1371869 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": 914553, "vin": [ { "gen": { "height": 914543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f90cdcc88e31f667b311b04455f9d437b5e14f8bfafc0ac285ef7edf633401" } } ], "extra": [ 1, 136, 147, 38, 176, 175, 179, 187, 49, 104, 84, 203, 210, 186, 26, 42, 35, 253, 177, 105, 225, 227, 27, 90, 88, 28, 170, 212, 45, 35, 241, 157, 172, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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