Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e09ad3b07a19396c6124e931dce145d9ebd37f3fb945a50d22ef4ac19a084618

Tx prefix hash: 8b221a5581a2c4f5e273d62e46c1ef17db5060e07ce47435b98284bf66a453b7
Tx public key: 041d44998bb3e9d64787f1825e464426c7de2530ac3c5156837509a568b95cf6
Timestamp: 1734409458 Timestamp [UCT]: 2024-12-17 04:24:18 Age [y:d:h:m:s]: 00:140:12:14:26
Block: 1176927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100212 RingCT/type: yes/0
Extra: 01041d44998bb3e9d64787f1825e464426c7de2530ac3c5156837509a568b95cf602110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65c72de0fe85367ef84d1369b610e7a28793c4a5d56f2d4db4f07aa4c54d580 0.600000000000 1663288 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": 1176937, "vin": [ { "gen": { "height": 1176927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65c72de0fe85367ef84d1369b610e7a28793c4a5d56f2d4db4f07aa4c54d580" } } ], "extra": [ 1, 4, 29, 68, 153, 139, 179, 233, 214, 71, 135, 241, 130, 94, 70, 68, 38, 199, 222, 37, 48, 172, 60, 81, 86, 131, 117, 9, 165, 104, 185, 92, 246, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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