Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 911d667f30905fcf66b6051f82757ba6a9d7e09c1a5f000a96ab4d038530129c

Tx prefix hash: a8a5c4578b42d1a44ba4accf5efd577b7b1fbda2597bc1dbc48b629cefe40f56
Tx public key: 92f4673af4f1023a43115793f4e848f997e27947336fe2bd9a940addff190f8d
Timestamp: 1707076933 Timestamp [UCT]: 2024-02-04 20:02:13 Age [y:d:h:m:s]: 01:052:19:49:11
Block: 950407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298809 RingCT/type: yes/0
Extra: 0192f4673af4f1023a43115793f4e848f997e27947336fe2bd9a940addff190f8d0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ceec74f7eb28f3010e9c59f958c9e22f768c39301ef7b19e7e2b5c089484ee3 0.600000000000 1409023 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": 950417, "vin": [ { "gen": { "height": 950407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ceec74f7eb28f3010e9c59f958c9e22f768c39301ef7b19e7e2b5c089484ee3" } } ], "extra": [ 1, 146, 244, 103, 58, 244, 241, 2, 58, 67, 17, 87, 147, 244, 232, 72, 249, 151, 226, 121, 71, 51, 111, 226, 189, 154, 148, 10, 221, 255, 25, 15, 141, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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