Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51fb5e8f3bb6e19cd03f2f002ccb7a9cfb002eca501190941ec8ef847f68fbc6

Tx prefix hash: 67d134a79d204e01168b6aadbe122994397e0d31ccf4804adc2d95df49267225
Tx public key: 1e64a4889f9e1ae2a0a339aa93a3a6816c7c5a1ebcbd092da92b01850643c138
Timestamp: 1726408094 Timestamp [UCT]: 2024-09-15 13:48:14 Age [y:d:h:m:s]: 00:116:23:40:06
Block: 1110680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83658 RingCT/type: yes/0
Extra: 011e64a4889f9e1ae2a0a339aa93a3a6816c7c5a1ebcbd092da92b01850643c13802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 723f88528d1282072d698b414d82a0bd2ba07556684c25c97ae8b23efc62457d 0.600000000000 1589371 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": 1110690, "vin": [ { "gen": { "height": 1110680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "723f88528d1282072d698b414d82a0bd2ba07556684c25c97ae8b23efc62457d" } } ], "extra": [ 1, 30, 100, 164, 136, 159, 158, 26, 226, 160, 163, 57, 170, 147, 163, 166, 129, 108, 124, 90, 30, 188, 189, 9, 45, 169, 43, 1, 133, 6, 67, 193, 56, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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