Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07bf9e45c03a74b9f06519a915ca83b8108bca05f3bcad76c913dc3847ad1d29

Tx prefix hash: 112738a0c52e1802668e3b6e79d89c6e29ad71df5f96c092fe1bc5a88f28429a
Tx public key: 5b61c83b094e20c4cf5cc3abdb96d817bcfaa826f859c5e1ea11becf53539131
Timestamp: 1634530560 Timestamp [UCT]: 2021-10-18 04:16:00 Age [y:d:h:m:s]: 03:045:22:20:04
Block: 355350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 810771 RingCT/type: yes/0
Extra: 015b61c83b094e20c4cf5cc3abdb96d817bcfaa826f859c5e1ea11becf5353913102110000003b36fe6557000000000000000000

1 output(s) for total of 40.793695032000 dcy

stealth address amount amount idx
00: 6b626b9dd8c3d85f4b654ca231530d606ab17a82e9a5f47fc14be7fc6aa3d6e1 40.793695032000 725510 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": 355360, "vin": [ { "gen": { "height": 355350 } } ], "vout": [ { "amount": 40793695032, "target": { "key": "6b626b9dd8c3d85f4b654ca231530d606ab17a82e9a5f47fc14be7fc6aa3d6e1" } } ], "extra": [ 1, 91, 97, 200, 59, 9, 78, 32, 196, 207, 92, 195, 171, 219, 150, 216, 23, 188, 250, 168, 38, 248, 89, 197, 225, 234, 17, 190, 207, 83, 83, 145, 49, 2, 17, 0, 0, 0, 59, 54, 254, 101, 87, 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