Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c57c6312d66362e93fd013062d38026f85584f765c48f6ebd0affda65af46a86

Tx prefix hash: a0e1b192fb92b4fde14688435b0fb5298756def2c6d323ff49bb30555f375e82
Tx public key: e671baa3e91ba285a39791c5e28e7f0c9a2a6d4a045250e8fc33c815ef7e83fa
Timestamp: 1755615247 Timestamp [UCT]: 2025-08-19 14:54:07 Age [y:d:h:m:s]: 00:047:08:23:57
Block: 1349933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33679 RingCT/type: yes/0
Extra: 01e671baa3e91ba285a39791c5e28e7f0c9a2a6d4a045250e8fc33c815ef7e83fa021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 273146e057365e04e070100e14320228d448618c1cc5f49e0b64e973df8e6141 0.600000000000 1837872 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": 1349943, "vin": [ { "gen": { "height": 1349933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "273146e057365e04e070100e14320228d448618c1cc5f49e0b64e973df8e6141" } } ], "extra": [ 1, 230, 113, 186, 163, 233, 27, 162, 133, 163, 151, 145, 197, 226, 142, 127, 12, 154, 42, 109, 74, 4, 82, 80, 232, 252, 51, 200, 21, 239, 126, 131, 250, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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