Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96f774fe8cf389fd1784516f26e45926e3c1798ceee23521d428871ec7d245df

Tx prefix hash: dea8d5a1143fd79b4c99038bef1fea81b7699333546a2ea0f0baac140827c431
Tx public key: 1e84576df30b228764fb66219e0e85791c1d377f06800d955f665d235b01d3f9
Timestamp: 1730338474 Timestamp [UCT]: 2024-10-31 01:34:34 Age [y:d:h:m:s]: 00:058:07:58:35
Block: 1143177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41741 RingCT/type: yes/0
Extra: 011e84576df30b228764fb66219e0e85791c1d377f06800d955f665d235b01d3f902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a89f50d2cec8a317ceaf2e0d6d631d8a0b0bd126237e8b9c84769791a211e3b4 0.600000000000 1627040 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": 1143187, "vin": [ { "gen": { "height": 1143177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a89f50d2cec8a317ceaf2e0d6d631d8a0b0bd126237e8b9c84769791a211e3b4" } } ], "extra": [ 1, 30, 132, 87, 109, 243, 11, 34, 135, 100, 251, 102, 33, 158, 14, 133, 121, 28, 29, 55, 127, 6, 128, 13, 149, 95, 102, 93, 35, 91, 1, 211, 249, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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