Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2780b6e8d597f68e2620845e73d6a87bbbf78e77e87425404a12cd2b6ed8375

Tx prefix hash: d4225c00385549993c3f429d309c49234c96f105ad341af1a757eecb4e50d5a8
Tx public key: 2e189f38ff730810b0dfb3a7f772c56a498dad1a2f735bdb87bf30938aecc7a6
Timestamp: 1705523963 Timestamp [UCT]: 2024-01-17 20:39:23 Age [y:d:h:m:s]: 00:288:04:04:15
Block: 937518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206367 RingCT/type: yes/0
Extra: 012e189f38ff730810b0dfb3a7f772c56a498dad1a2f735bdb87bf30938aecc7a602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b52eb4529be39dcd13d5462506e8304941fd01f1a7f2e591295a4ebd759e3456 0.600000000000 1395574 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": 937528, "vin": [ { "gen": { "height": 937518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b52eb4529be39dcd13d5462506e8304941fd01f1a7f2e591295a4ebd759e3456" } } ], "extra": [ 1, 46, 24, 159, 56, 255, 115, 8, 16, 176, 223, 179, 167, 247, 114, 197, 106, 73, 141, 173, 26, 47, 115, 91, 219, 135, 191, 48, 147, 138, 236, 199, 166, 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