Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa058f56df68bd8ce84396db092f177c64c819a82ed00c49ae988e8f1c44a4d8

Tx prefix hash: 5b17c056b22fa63b0730a833bf348065d116b808201e7a66cd427325d76efd7d
Tx public key: ea0c7833bc5e6315a31c866d0746bae976dbf3241620b2146e5109ff76aa893d
Timestamp: 1751228470 Timestamp [UCT]: 2025-06-29 20:21:10 Age [y:d:h:m:s]: 00:143:18:48:16
Block: 1315392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100913 RingCT/type: yes/0
Extra: 01ea0c7833bc5e6315a31c866d0746bae976dbf3241620b2146e5109ff76aa893d02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54b6a9cd0c710c5608c64a38a334b662e41b0b28426576ba51990c5b423949e6 0.600000000000 1803047 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": 1315402, "vin": [ { "gen": { "height": 1315392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54b6a9cd0c710c5608c64a38a334b662e41b0b28426576ba51990c5b423949e6" } } ], "extra": [ 1, 234, 12, 120, 51, 188, 94, 99, 21, 163, 28, 134, 109, 7, 70, 186, 233, 118, 219, 243, 36, 22, 32, 178, 20, 110, 81, 9, 255, 118, 170, 137, 61, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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