Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c2488dc8bea14a7a32ba98f574c8129a27e3b71018b7aeef7cdfd8e71c0fa1

Tx prefix hash: 1d0e5b056a3e9b4244a64b76d36ed5607703265ccd74d539fcecfe9d5274eba9
Tx public key: 978fb9e03731226e9edfc0b728871b0b7118a5bd9b80f225872c8af5de873307
Timestamp: 1732318075 Timestamp [UCT]: 2024-11-22 23:27:55 Age [y:d:h:m:s]: 00:001:05:58:48
Block: 1159591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 884 RingCT/type: yes/0
Extra: 01978fb9e03731226e9edfc0b728871b0b7118a5bd9b80f225872c8af5de873307021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f2d13faecdf4c9904b9fdbd455689966c7ead34b497f16524a39852fa59100e 0.600000000000 1645230 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": 1159601, "vin": [ { "gen": { "height": 1159591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f2d13faecdf4c9904b9fdbd455689966c7ead34b497f16524a39852fa59100e" } } ], "extra": [ 1, 151, 143, 185, 224, 55, 49, 34, 110, 158, 223, 192, 183, 40, 135, 27, 11, 113, 24, 165, 189, 155, 128, 242, 37, 135, 44, 138, 245, 222, 135, 51, 7, 2, 17, 0, 0, 0, 5, 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