Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ff2feb0b09de03b6dfd9bfc3485addeaa9a6903884f04a720b9273c601a7bd7

Tx prefix hash: 280034a387bea4222c903222eaaad28cbfa8e264f0989fd58ce807e61955383d
Tx public key: 5c79387c7aec4807f5085d512915515b15e526b4cb3f5a788701df55f0dabb93
Timestamp: 1737302530 Timestamp [UCT]: 2025-01-19 16:02:10 Age [y:d:h:m:s]: 00:332:02:58:24
Block: 1200816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234945 RingCT/type: yes/0
Extra: 015c79387c7aec4807f5085d512915515b15e526b4cb3f5a788701df55f0dabb930211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e37cd3d8a610ed51005899d3a468a48decd5bb8c841df0fa5dfa0b06aab373a6 0.600000000000 1687463 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": 1200826, "vin": [ { "gen": { "height": 1200816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e37cd3d8a610ed51005899d3a468a48decd5bb8c841df0fa5dfa0b06aab373a6" } } ], "extra": [ 1, 92, 121, 56, 124, 122, 236, 72, 7, 245, 8, 93, 81, 41, 21, 81, 91, 21, 229, 38, 180, 203, 63, 90, 120, 135, 1, 223, 85, 240, 218, 187, 147, 2, 17, 0, 0, 0, 1, 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