Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec8f5c2ba4e3983fca1ea6d389f2aedae998853844bd1aac789e14a0977bb622

Tx prefix hash: 33615b31126fe5e5d2b71be7c65d8c1d566b1ed8ad8f6cb4f5c97fdb819ef330
Tx public key: 7e722ab59f87b6328a60235d4cb5ba2b82ac07245dc6fd70956756a4c671d505
Timestamp: 1737222284 Timestamp [UCT]: 2025-01-18 17:44:44 Age [y:d:h:m:s]: 00:150:08:35:10
Block: 1200150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107205 RingCT/type: yes/0
Extra: 017e722ab59f87b6328a60235d4cb5ba2b82ac07245dc6fd70956756a4c671d5050211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 020e0726a0461755d753479cc336d672221008a6aa1f8599d87a0d377004da33 0.600000000000 1686791 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": 1200160, "vin": [ { "gen": { "height": 1200150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "020e0726a0461755d753479cc336d672221008a6aa1f8599d87a0d377004da33" } } ], "extra": [ 1, 126, 114, 42, 181, 159, 135, 182, 50, 138, 96, 35, 93, 76, 181, 186, 43, 130, 172, 7, 36, 93, 198, 253, 112, 149, 103, 86, 164, 198, 113, 213, 5, 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