Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6274232ce129e18b0a9c0962070503ee7aee3bfbc5abe6508749a9c0a5c4c9

Tx prefix hash: 360dc370191b69b8366bb59161db8ff6b758dec0294adc3b1b51ef29c499578a
Tx public key: dd923f384b452c614272e34f89a3d7de30b22f3a3418a1b60d1a32c92aaac592
Timestamp: 1710379110 Timestamp [UCT]: 2024-03-14 01:18:30 Age [y:d:h:m:s]: 01:062:11:15:21
Block: 977810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305646 RingCT/type: yes/0
Extra: 01dd923f384b452c614272e34f89a3d7de30b22f3a3418a1b60d1a32c92aaac59202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cfb632a81a1203a33c4d1da74ad62d35184d3ffe6842d1da4b26d7aff5c34c9 0.600000000000 1437817 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": 977820, "vin": [ { "gen": { "height": 977810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cfb632a81a1203a33c4d1da74ad62d35184d3ffe6842d1da4b26d7aff5c34c9" } } ], "extra": [ 1, 221, 146, 63, 56, 75, 69, 44, 97, 66, 114, 227, 79, 137, 163, 215, 222, 48, 178, 47, 58, 52, 24, 161, 182, 13, 26, 50, 201, 42, 170, 197, 146, 2, 17, 0, 0, 0, 1, 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