Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 374858a76b890b7a9614f365f67ad36b99c6811d1bb6d417af33fd9a8b32ce5f

Tx prefix hash: 4f1e580af10d3efcae9fb523fa6c5fde286670eb51e215c0926d19c79b7cb0b3
Tx public key: 792bfc295500e6350969b4a9af05dd2f746e415c551afbe0d88728afccaa8e7e
Timestamp: 1742412361 Timestamp [UCT]: 2025-03-19 19:26:01 Age [y:d:h:m:s]: 00:319:01:33:51
Block: 1242909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225675 RingCT/type: yes/0
Extra: 01792bfc295500e6350969b4a9af05dd2f746e415c551afbe0d88728afccaa8e7e021100000004bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e5cb17c7b25780610763e76bbc5f68548ff1402b361da5d3ac863edaa6bef11 0.600000000000 1729888 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": 1242919, "vin": [ { "gen": { "height": 1242909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e5cb17c7b25780610763e76bbc5f68548ff1402b361da5d3ac863edaa6bef11" } } ], "extra": [ 1, 121, 43, 252, 41, 85, 0, 230, 53, 9, 105, 180, 169, 175, 5, 221, 47, 116, 110, 65, 92, 85, 26, 251, 224, 216, 135, 40, 175, 204, 170, 142, 126, 2, 17, 0, 0, 0, 4, 191, 167, 118, 35, 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