Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29dbb15a446d7aea1476c3d73083bd34481b5a3fdd8aa3cd18eb98c9e77924aa

Tx prefix hash: 9b70a3f5dbd58137796f391ad9c647ab5694547c1c80e57c3b40ccbb6087af80
Tx public key: e99d4cc936f95495c19f34d2b993a1561048d80c7d8bcb1acbc415db31ba4a87
Timestamp: 1755903119 Timestamp [UCT]: 2025-08-22 22:51:59 Age [y:d:h:m:s]: 00:087:08:44:27
Block: 1352282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62377 RingCT/type: yes/0
Extra: 01e99d4cc936f95495c19f34d2b993a1561048d80c7d8bcb1acbc415db31ba4a870211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad6802527a83f8955fbf94a34bcee6c3dadd0ab6e83ac6256a94b83d7697fc9 0.600000000000 1840245 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": 1352292, "vin": [ { "gen": { "height": 1352282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad6802527a83f8955fbf94a34bcee6c3dadd0ab6e83ac6256a94b83d7697fc9" } } ], "extra": [ 1, 233, 157, 76, 201, 54, 249, 84, 149, 193, 159, 52, 210, 185, 147, 161, 86, 16, 72, 216, 12, 125, 139, 203, 26, 203, 196, 21, 219, 49, 186, 74, 135, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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