Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3d0688fe7184073d758e563afdb3cfc26865f13802d5f41e22e62ed92a593f7

Tx prefix hash: 32613070231f770d1c31cec5d5e22f5a156b19bfb03281353a394d9ff0887c49
Tx public key: e4627a10d6c7b310c0e5cf65f001d13f494ee32dc27f298404de1a32fcc2ed2b
Timestamp: 1749063037 Timestamp [UCT]: 2025-06-04 18:50:37 Age [y:d:h:m:s]: 00:158:12:47:02
Block: 1297968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110969 RingCT/type: yes/0
Extra: 01e4627a10d6c7b310c0e5cf65f001d13f494ee32dc27f298404de1a32fcc2ed2b021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e7101f1fe3cc32282d352bf758ef57cc354f5e2122c7d661ebcccf4983ad78 0.600000000000 1785491 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": 1297978, "vin": [ { "gen": { "height": 1297968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e7101f1fe3cc32282d352bf758ef57cc354f5e2122c7d661ebcccf4983ad78" } } ], "extra": [ 1, 228, 98, 122, 16, 214, 199, 179, 16, 192, 229, 207, 101, 240, 1, 209, 63, 73, 78, 227, 45, 194, 127, 41, 132, 4, 222, 26, 50, 252, 194, 237, 43, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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