Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4df0b9fe74f5066a653490c3950d8ccbcc9d45780c4edc99d19c4449a2ffa224

Tx prefix hash: 8623e3c8073c98a9d7587530f550bdfd9ac7a060c51eb0420f9ede4db7398594
Tx public key: 53b50a7e38229a70e17602adce112ea7f9fa8cbcca2b3a016437d8ef0a3400d3
Timestamp: 1760500472 Timestamp [UCT]: 2025-10-15 03:54:32 Age [y:d:h:m:s]: 00:030:00:45:52
Block: 1390209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21502 RingCT/type: yes/0
Extra: 0153b50a7e38229a70e17602adce112ea7f9fa8cbcca2b3a016437d8ef0a3400d30211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 792b7f33f148a5a68e1104e22a82f590299c875e294c5ccb017a7c53b84e5176 0.600000000000 1878444 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": 1390219, "vin": [ { "gen": { "height": 1390209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "792b7f33f148a5a68e1104e22a82f590299c875e294c5ccb017a7c53b84e5176" } } ], "extra": [ 1, 83, 181, 10, 126, 56, 34, 154, 112, 225, 118, 2, 173, 206, 17, 46, 167, 249, 250, 140, 188, 202, 43, 58, 1, 100, 55, 216, 239, 10, 52, 0, 211, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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