Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91d9ea11f9eb20c4138bf345301e31ee62f9c025a51e964d65fae153fa9e31ea

Tx prefix hash: 89088534ea45b3432776010dc4b78ea5c5aa4aa11d3089158a19e37e0f13866a
Tx public key: 9dd1e8f52194dded873bf728615eb48af377a45319a1e1107b506b20ac9ca2cf
Timestamp: 1712678163 Timestamp [UCT]: 2024-04-09 15:56:03 Age [y:d:h:m:s]: 01:026:16:40:23
Block: 996830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280065 RingCT/type: yes/0
Extra: 019dd1e8f52194dded873bf728615eb48af377a45319a1e1107b506b20ac9ca2cf02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b51c15c2332f268c64541716d3f88db3adb71f2ea0dd015dd2b8519c9b7b100b 0.600000000000 1457258 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": 996840, "vin": [ { "gen": { "height": 996830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b51c15c2332f268c64541716d3f88db3adb71f2ea0dd015dd2b8519c9b7b100b" } } ], "extra": [ 1, 157, 209, 232, 245, 33, 148, 221, 237, 135, 59, 247, 40, 97, 94, 180, 138, 243, 119, 164, 83, 25, 161, 225, 16, 123, 80, 107, 32, 172, 156, 162, 207, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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