Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63770887b1b7f4ae44778b710fcb9921944272824ac07e0ebeebb8cd4d39f606

Tx prefix hash: 0c52d80a257d5af75066264d143919e0f35be70d1bdda6ef7daca45ecae51c18
Tx public key: 434dc370cfc01332b3d6d7c30c97b68ebde3cec575d9b5c81d937e93ed311c55
Timestamp: 1725870275 Timestamp [UCT]: 2024-09-09 08:24:35 Age [y:d:h:m:s]: 00:201:01:15:16
Block: 1106223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143524 RingCT/type: yes/0
Extra: 01434dc370cfc01332b3d6d7c30c97b68ebde3cec575d9b5c81d937e93ed311c55021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25a4c8971438964ad1505765876d42582b54f0da5ca36ddb8274a8f47b6cbcc2 0.600000000000 1583822 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": 1106233, "vin": [ { "gen": { "height": 1106223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25a4c8971438964ad1505765876d42582b54f0da5ca36ddb8274a8f47b6cbcc2" } } ], "extra": [ 1, 67, 77, 195, 112, 207, 192, 19, 50, 179, 214, 215, 195, 12, 151, 182, 142, 189, 227, 206, 197, 117, 217, 181, 200, 29, 147, 126, 147, 237, 49, 28, 85, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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