Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3018e7fcee3c7e6fad92c954b09272f041cc654079eff1b8c227ba5f74288ae

Tx prefix hash: 549c0fb5c1aa2996f34a8b9b27dca5fb8c5c6ae490f3c6f855c672f6c22e08f0
Tx public key: 3692b71b2f3ac5766f66287193d01e4923bac21a5e8e8c7e9d7f418a342de87b
Timestamp: 1731991355 Timestamp [UCT]: 2024-11-19 04:42:35 Age [y:d:h:m:s]: 00:150:02:09:15
Block: 1156880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107091 RingCT/type: yes/0
Extra: 013692b71b2f3ac5766f66287193d01e4923bac21a5e8e8c7e9d7f418a342de87b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dfe7d02dec75880e6abe22393cdb08a78c2f8c2bb1273416eb9ddc6d872116a 0.600000000000 1642503 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": 1156890, "vin": [ { "gen": { "height": 1156880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dfe7d02dec75880e6abe22393cdb08a78c2f8c2bb1273416eb9ddc6d872116a" } } ], "extra": [ 1, 54, 146, 183, 27, 47, 58, 197, 118, 111, 102, 40, 113, 147, 208, 30, 73, 35, 186, 194, 26, 94, 142, 140, 126, 157, 127, 65, 138, 52, 45, 232, 123, 2, 17, 0, 0, 0, 5, 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