Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4fd8f62889b7c843c5ca26fd2a4adf98eedc07547bcfd9ed7a729f8823c7d82

Tx prefix hash: d75428c9561b36f2aaceac0eef02d008f600682f663acd7326077a042d055b5b
Tx public key: bc42c9b9071cabb196221cfe36b048e409863ae71b3c69a6594b263c2f617b35
Timestamp: 1755184901 Timestamp [UCT]: 2025-08-14 15:21:41 Age [y:d:h:m:s]: 00:047:04:11:37
Block: 1346738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33183 RingCT/type: yes/0
Extra: 01bc42c9b9071cabb196221cfe36b048e409863ae71b3c69a6594b263c2f617b350211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c0ad593c8a0fb69b7941ee84bcba92a3a9aec3e3a609498149a9861bccd557a 0.600000000000 1834643 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": 1346748, "vin": [ { "gen": { "height": 1346738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c0ad593c8a0fb69b7941ee84bcba92a3a9aec3e3a609498149a9861bccd557a" } } ], "extra": [ 1, 188, 66, 201, 185, 7, 28, 171, 177, 150, 34, 28, 254, 54, 176, 72, 228, 9, 134, 58, 231, 27, 60, 105, 166, 89, 75, 38, 60, 47, 97, 123, 53, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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