Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a9ba1dc72fa2b0a96f2bc27f2779b81fe75551e1b2fd88e6af79da69f1a1bbf

Tx prefix hash: 387b6680e32d0136aa45fa47531acf24c614459aa367365a8afc249241f60456
Tx public key: acb2a2bf57c24dcc3055e640d70b8857363da3130e1d2e1b1ff741178986f18c
Timestamp: 1737515058 Timestamp [UCT]: 2025-01-22 03:04:18 Age [y:d:h:m:s]: 00:327:00:20:33
Block: 1202565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231299 RingCT/type: yes/0
Extra: 01acb2a2bf57c24dcc3055e640d70b8857363da3130e1d2e1b1ff741178986f18c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae553aae79b8ea22593d4fee3acd66069dc325fe6c1744ccc9407935cb1db593 0.600000000000 1689230 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": 1202575, "vin": [ { "gen": { "height": 1202565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae553aae79b8ea22593d4fee3acd66069dc325fe6c1744ccc9407935cb1db593" } } ], "extra": [ 1, 172, 178, 162, 191, 87, 194, 77, 204, 48, 85, 230, 64, 215, 11, 136, 87, 54, 61, 163, 19, 14, 29, 46, 27, 31, 247, 65, 23, 137, 134, 241, 140, 2, 17, 0, 0, 0, 4, 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