Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 772e24947d033f4a60a6224b2e333dfa532340b5e4f68a7d8e55e6215a4ab564

Tx prefix hash: e3557a19b20e7eca65b696ce4a9fba99230345adf737b014a6a5149ad99198dd
Tx public key: 378823657c51d9b6c631e692ea6772d944fc926b7e29fb25a3f59c2420a811b3
Timestamp: 1736662594 Timestamp [UCT]: 2025-01-12 06:16:34 Age [y:d:h:m:s]: 00:079:18:58:20
Block: 1195551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56799 RingCT/type: yes/0
Extra: 01378823657c51d9b6c631e692ea6772d944fc926b7e29fb25a3f59c2420a811b30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a42449757be784ae61e422752360a118f85fc355383a38bd2cadd5e9565a48f9 0.600000000000 1682142 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": 1195561, "vin": [ { "gen": { "height": 1195551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a42449757be784ae61e422752360a118f85fc355383a38bd2cadd5e9565a48f9" } } ], "extra": [ 1, 55, 136, 35, 101, 124, 81, 217, 182, 198, 49, 230, 146, 234, 103, 114, 217, 68, 252, 146, 107, 126, 41, 251, 37, 163, 245, 156, 36, 32, 168, 17, 179, 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