Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d8ad9bdd30b312a8d0704c7f0ac6fbe621d9a7f98d6a3568048f97bf43de803

Tx prefix hash: 2d318ac8ea6333ecdf98cfb952758cfb35b274418f94ab4465343be3287a258d
Tx public key: 8b9d2029f4b430271a217d88ec1c8b9cf09ba95d132a5673421bcc16e27ce4df
Timestamp: 1738962384 Timestamp [UCT]: 2025-02-07 21:06:24 Age [y:d:h:m:s]: 00:285:17:23:45
Block: 1214334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201954 RingCT/type: yes/0
Extra: 018b9d2029f4b430271a217d88ec1c8b9cf09ba95d132a5673421bcc16e27ce4df02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ce572dbc0e0201451fa01c332b0f00ac5f7feeaabe70c8648dd05c40197bb92 0.600000000000 1701123 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": 1214344, "vin": [ { "gen": { "height": 1214334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ce572dbc0e0201451fa01c332b0f00ac5f7feeaabe70c8648dd05c40197bb92" } } ], "extra": [ 1, 139, 157, 32, 41, 244, 180, 48, 39, 26, 33, 125, 136, 236, 28, 139, 156, 240, 155, 169, 93, 19, 42, 86, 115, 66, 27, 204, 22, 226, 124, 228, 223, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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