Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f35e7d936a64eb02d5453c7eb09a3031692437d7ca31651665d5462fc26cf13c

Tx prefix hash: 89857b4751d0c757922eb61b161ec702d9c335a8f36b6c7a48a75da1ccb540d2
Tx public key: 9d3f85f019c96bb9937a30bd090a8fea4b5388c3046574a75ed8150aad618a0b
Timestamp: 1735471192 Timestamp [UCT]: 2024-12-29 11:19:52 Age [y:d:h:m:s]: 00:098:12:12:17
Block: 1185684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70184 RingCT/type: yes/0
Extra: 019d3f85f019c96bb9937a30bd090a8fea4b5388c3046574a75ed8150aad618a0b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02fd194b1735fcfa9a031abe80ced3a108113e5d6f12fb63ea0e2f3c271a3bad 0.600000000000 1672159 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": 1185694, "vin": [ { "gen": { "height": 1185684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02fd194b1735fcfa9a031abe80ced3a108113e5d6f12fb63ea0e2f3c271a3bad" } } ], "extra": [ 1, 157, 63, 133, 240, 25, 201, 107, 185, 147, 122, 48, 189, 9, 10, 143, 234, 75, 83, 136, 195, 4, 101, 116, 167, 94, 216, 21, 10, 173, 97, 138, 11, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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