Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5824719987c86ea3dcfbf91f3edc5685463ec0c187f5d2a484716d123d7c1f38

Tx prefix hash: 0c1bc4199c19100dd1b271101c57fb0999088cdebd64e961e800c24d402bf461
Tx public key: 643bd3a1e5a1f533c3aa5b7010be2e2a1bbaba4adb3870ff13387e0916b42517
Timestamp: 1713983424 Timestamp [UCT]: 2024-04-24 18:30:24 Age [y:d:h:m:s]: 00:329:04:56:46
Block: 1007673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235359 RingCT/type: yes/0
Extra: 01643bd3a1e5a1f533c3aa5b7010be2e2a1bbaba4adb3870ff13387e0916b4251702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d289b3cf3fff06f409ed5b830a1449423ae17a60c4406fca262e04661e5c66c 0.600000000000 1469091 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": 1007683, "vin": [ { "gen": { "height": 1007673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d289b3cf3fff06f409ed5b830a1449423ae17a60c4406fca262e04661e5c66c" } } ], "extra": [ 1, 100, 59, 211, 161, 229, 161, 245, 51, 195, 170, 91, 112, 16, 190, 46, 42, 27, 186, 186, 74, 219, 56, 112, 255, 19, 56, 126, 9, 22, 180, 37, 23, 2, 17, 0, 0, 0, 1, 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