Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b53097e424e5b6913ec5b604407b0c9c372ee436c9221ce0a340c38cb61d68f

Tx prefix hash: 303fcca66d92261f51bca297f12a6fdb6d5a9770f12e5a4de7418e08fce16d09
Tx public key: ed357895c8fea0950471a2a5c8117e4e42ad2cff60f741bd7a961672030954cf
Timestamp: 1683631860 Timestamp [UCT]: 2023-05-09 11:31:00 Age [y:d:h:m:s]: 01:247:17:19:35
Block: 756304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438491 RingCT/type: yes/0
Extra: 01ed357895c8fea0950471a2a5c8117e4e42ad2cff60f741bd7a961672030954cf02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.914481108000 dcy

stealth address amount amount idx
00: 813528ac2f933f9595899af9550167c965a6e2c9df4701de6f12130784626a0b 1.914481108000 1204665 of 0

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": 756314, "vin": [ { "gen": { "height": 756304 } } ], "vout": [ { "amount": 1914481108, "target": { "key": "813528ac2f933f9595899af9550167c965a6e2c9df4701de6f12130784626a0b" } } ], "extra": [ 1, 237, 53, 120, 149, 200, 254, 160, 149, 4, 113, 162, 165, 200, 17, 126, 78, 66, 173, 44, 255, 96, 247, 65, 189, 122, 150, 22, 114, 3, 9, 84, 207, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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