Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c168cb7101ed3023374ef2984bb1b757422358305ddda1d83a296ceda08182e

Tx prefix hash: 9fa6f1bbac83aae66448929a108a92e9a425dcf8216da8a8f1a49b4260fb51c1
Tx public key: b0bc73e4d302b49d21c423f563a5934c7bbb72df18d80bc1dddca9ca531ba3bb
Timestamp: 1722336396 Timestamp [UCT]: 2024-07-30 10:46:36 Age [y:d:h:m:s]: 00:116:23:39:57
Block: 1076931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83693 RingCT/type: yes/0
Extra: 01b0bc73e4d302b49d21c423f563a5934c7bbb72df18d80bc1dddca9ca531ba3bb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d83bb92d52db647606ff0b552083c00f917755eb07e68ff53c71e8542febc85 0.600000000000 1549474 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": 1076941, "vin": [ { "gen": { "height": 1076931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d83bb92d52db647606ff0b552083c00f917755eb07e68ff53c71e8542febc85" } } ], "extra": [ 1, 176, 188, 115, 228, 211, 2, 180, 157, 33, 196, 35, 245, 99, 165, 147, 76, 123, 187, 114, 223, 24, 216, 11, 193, 221, 220, 169, 202, 83, 27, 163, 187, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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