Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c72c7bee0be5e04d984cb582243b13b46594ffba69fa46f116f8c9615f2889d

Tx prefix hash: cf8781ad973cabb2704df0d281d9162dcd59cee5bf2316fe0f68fb1f2ff0c3bc
Tx public key: aa7e45c44d2e9ad8d840fe5a1cc7f307ea4ff088412b40e630ff421c7c4ad021
Timestamp: 1710828527 Timestamp [UCT]: 2024-03-19 06:08:47 Age [y:d:h:m:s]: 01:262:20:41:34
Block: 981537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446584 RingCT/type: yes/0
Extra: 01aa7e45c44d2e9ad8d840fe5a1cc7f307ea4ff088412b40e630ff421c7c4ad02102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e5d1d33e3ae4fc77e44497a29b7f4629a8c132ea174b1443ffd816dc716c73c 0.600000000000 1441634 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": 981547, "vin": [ { "gen": { "height": 981537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e5d1d33e3ae4fc77e44497a29b7f4629a8c132ea174b1443ffd816dc716c73c" } } ], "extra": [ 1, 170, 126, 69, 196, 77, 46, 154, 216, 216, 64, 254, 90, 28, 199, 243, 7, 234, 79, 240, 136, 65, 43, 64, 230, 48, 255, 66, 28, 124, 74, 208, 33, 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