Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb84a30e8b4c9256d7969fe7422735e3c30f5e7787036a2f266769e75b0c601

Tx prefix hash: 8a96dc81c182b7c0877f28864b644d92a20e62b94f659b96b090330fefd4540e
Tx public key: 43d5ad9b6bc5e50e0e21c2607f56032ca1c329f02f6392e0da0ba158144dfe0e
Timestamp: 1765515843 Timestamp [UCT]: 2025-12-12 05:04:03 Age [y:d:h:m:s]: 00:011:20:52:03
Block: 1431768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8494 RingCT/type: yes/0
Extra: 0143d5ad9b6bc5e50e0e21c2607f56032ca1c329f02f6392e0da0ba158144dfe0e02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85048b87fff1230b01b1ec50b43f8c7c51ee5c693bb178c17fe6841a93a9080d 0.600000000000 1920541 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": 1431778, "vin": [ { "gen": { "height": 1431768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85048b87fff1230b01b1ec50b43f8c7c51ee5c693bb178c17fe6841a93a9080d" } } ], "extra": [ 1, 67, 213, 173, 155, 107, 197, 229, 14, 14, 33, 194, 96, 127, 86, 3, 44, 161, 195, 41, 240, 47, 99, 146, 224, 218, 11, 161, 88, 20, 77, 254, 14, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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