Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf96f1b9aa552ae4360bea890e2fcb26e66abb81456e7d45ab45bac4fd743165

Tx prefix hash: 2a1522f503300334298822c214e39e2b12ef785e5640ef5b3909ea6db14fc28c
Tx public key: 952f15d6702a6f8067779c0ed351e030a5da55f05b850fe8db9daa9ac09607e3
Timestamp: 1698117146 Timestamp [UCT]: 2023-10-24 03:12:26 Age [y:d:h:m:s]: 01:125:12:50:11
Block: 876338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350705 RingCT/type: yes/0
Extra: 01952f15d6702a6f8067779c0ed351e030a5da55f05b850fe8db9daa9ac09607e3021100000007faf35c9c000000000000000000

1 output(s) for total of 0.766175815000 dcy

stealth address amount amount idx
00: c8b62fd8fc4efa7df8a4503e4b7849c54f4627390749d89efd70e2fb2f1cdb60 0.766175815000 1331658 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": 876348, "vin": [ { "gen": { "height": 876338 } } ], "vout": [ { "amount": 766175815, "target": { "key": "c8b62fd8fc4efa7df8a4503e4b7849c54f4627390749d89efd70e2fb2f1cdb60" } } ], "extra": [ 1, 149, 47, 21, 214, 112, 42, 111, 128, 103, 119, 156, 14, 211, 81, 224, 48, 165, 218, 85, 240, 91, 133, 15, 232, 219, 157, 170, 154, 192, 150, 7, 227, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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