Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a09d01b8045ac8c751e35778ef92603b13a0227d952a515e6b9647b894b2f2d

Tx prefix hash: 54a8c573958b8f3b3d55429c2d895fd173210e79ac6280fa6850ddb225ca2675
Tx public key: f66ca75a833bbeccbbcac56a31fdcf3e16a4d422f4c5d64ce552bd781bef0a90
Timestamp: 1735764177 Timestamp [UCT]: 2025-01-01 20:42:57 Age [y:d:h:m:s]: 00:074:14:48:35
Block: 1188111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53137 RingCT/type: yes/0
Extra: 01f66ca75a833bbeccbbcac56a31fdcf3e16a4d422f4c5d64ce552bd781bef0a900211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f70eaf31c523eb6ad2eb183af98fe0248c44170533ae9003a2ae67d39a300ac 0.600000000000 1674610 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": 1188121, "vin": [ { "gen": { "height": 1188111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f70eaf31c523eb6ad2eb183af98fe0248c44170533ae9003a2ae67d39a300ac" } } ], "extra": [ 1, 246, 108, 167, 90, 131, 59, 190, 204, 187, 202, 197, 106, 49, 253, 207, 62, 22, 164, 212, 34, 244, 197, 214, 76, 229, 82, 189, 120, 27, 239, 10, 144, 2, 17, 0, 0, 0, 2, 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