Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4ec17a5de08fc863f92c97626f56fc5a292fb9622a774da3dcdd7c43ac5304

Tx prefix hash: ecf508e0b8ead599d9f902e13f66dcead8b0e733914b302debf0baf204aa5ba0
Tx public key: 8152ec55d054def2494b4b13c3f0872115b40149cbfc4a76cdd3434f8549baa0
Timestamp: 1760945332 Timestamp [UCT]: 2025-10-20 07:28:52 Age [y:d:h:m:s]: 00:082:09:27:53
Block: 1393911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58991 RingCT/type: yes/0
Extra: 018152ec55d054def2494b4b13c3f0872115b40149cbfc4a76cdd3434f8549baa00211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03f70d9ac7dd448c9bba2412f72bfcd981cb4f9e6489b194cdc00406826edaa8 0.600000000000 1882178 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": 1393921, "vin": [ { "gen": { "height": 1393911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03f70d9ac7dd448c9bba2412f72bfcd981cb4f9e6489b194cdc00406826edaa8" } } ], "extra": [ 1, 129, 82, 236, 85, 208, 84, 222, 242, 73, 75, 75, 19, 195, 240, 135, 33, 21, 180, 1, 73, 203, 252, 74, 118, 205, 211, 67, 79, 133, 73, 186, 160, 2, 17, 0, 0, 0, 2, 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