Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1ccfd046b9b14a8f6d8617576230693b7a773d45d25bdfe6716696522e2511

Tx prefix hash: 3239263fe46180a7a79894de470eceeacbf00fe3f67455fd6fb80d6ae81d6159
Tx public key: d3a67387e9f05eccb003cda66d1d9bb5fda4768142d3d24a06fb71d0eb26f7a0
Timestamp: 1751569616 Timestamp [UCT]: 2025-07-03 19:06:56 Age [y:d:h:m:s]: 00:131:07:56:02
Block: 1318116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92111 RingCT/type: yes/0
Extra: 01d3a67387e9f05eccb003cda66d1d9bb5fda4768142d3d24a06fb71d0eb26f7a0021100000007d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe156da46b755d28005267c287697b4b0c94322cdd4f82dfce188538825c2295 0.600000000000 1805789 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": 1318126, "vin": [ { "gen": { "height": 1318116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe156da46b755d28005267c287697b4b0c94322cdd4f82dfce188538825c2295" } } ], "extra": [ 1, 211, 166, 115, 135, 233, 240, 94, 204, 176, 3, 205, 166, 109, 29, 155, 181, 253, 164, 118, 129, 66, 211, 210, 74, 6, 251, 113, 208, 235, 38, 247, 160, 2, 17, 0, 0, 0, 7, 216, 231, 210, 65, 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