Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 077ce9b33f7a0d67085548ad50165e5b09a625283e2fbbbf5b2c895e5e043cf3

Tx prefix hash: 88f547a1905d729edbf31ba8255f4249ca3340bf69ea057bf0ec51e9c5cb89ca
Tx public key: d8b535e08cc576656f0d5b7e126df8d1dcbf4991cc68269dbf70615597228e61
Timestamp: 1718525791 Timestamp [UCT]: 2024-06-16 08:16:31 Age [y:d:h:m:s]: 01:145:18:33:12
Block: 1045348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362724 RingCT/type: yes/0
Extra: 01d8b535e08cc576656f0d5b7e126df8d1dcbf4991cc68269dbf70615597228e610211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36a000848fb727f5269e1294a3e205354fa03d1a5e972c47ffc32e965706a158 0.600000000000 1514893 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": 1045358, "vin": [ { "gen": { "height": 1045348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36a000848fb727f5269e1294a3e205354fa03d1a5e972c47ffc32e965706a158" } } ], "extra": [ 1, 216, 181, 53, 224, 140, 197, 118, 101, 111, 13, 91, 126, 18, 109, 248, 209, 220, 191, 73, 145, 204, 104, 38, 157, 191, 112, 97, 85, 151, 34, 142, 97, 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