Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55afd407273eab732c0fa6a9f02c103a121eae5ecd6007f34b6c7551012810b5

Tx prefix hash: 98c544a73793451a605e209944d30aa4b267994ba4a213efb639d06372477021
Tx public key: ad92ef57bdc20e50f987344091f54df32519f897ff09e90f966c0f94d8c03b8f
Timestamp: 1715484655 Timestamp [UCT]: 2024-05-12 03:30:55 Age [y:d:h:m:s]: 00:332:15:02:41
Block: 1020151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237727 RingCT/type: yes/0
Extra: 01ad92ef57bdc20e50f987344091f54df32519f897ff09e90f966c0f94d8c03b8f02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 814eeea784f1cc511201ee872176067b2ab2ffc9c42a9a8555ff3d6e21c08da0 0.600000000000 1484210 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": 1020161, "vin": [ { "gen": { "height": 1020151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "814eeea784f1cc511201ee872176067b2ab2ffc9c42a9a8555ff3d6e21c08da0" } } ], "extra": [ 1, 173, 146, 239, 87, 189, 194, 14, 80, 249, 135, 52, 64, 145, 245, 77, 243, 37, 25, 248, 151, 255, 9, 233, 15, 150, 108, 15, 148, 216, 192, 59, 143, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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