Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e76f6e335be17038b341c477502188838a535f602e6fdb9082e6310c529e9a2

Tx prefix hash: c6a2eb262d1ac55c6cfec0c08e74e72d49f4618960550c103d2b09942202ec59
Tx public key: 9d1c9a7aa8794e5f49840f082eae30e080449be7138e727df41a7d9ed34aba72
Timestamp: 1663855466 Timestamp [UCT]: 2022-09-22 14:04:26 Age [y:d:h:m:s]: 02:179:04:01:40
Block: 593413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649452 RingCT/type: yes/0
Extra: 019d1c9a7aa8794e5f49840f082eae30e080449be7138e727df41a7d9ed34aba7202110000000175e3f0e9000000000000000000

1 output(s) for total of 6.634015211000 dcy

stealth address amount amount idx
00: 7f7b7dbff286cd02ce2d1aab084a6ddca02628e9238735f96e204e144eeb3b2d 6.634015211000 1028196 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": 593423, "vin": [ { "gen": { "height": 593413 } } ], "vout": [ { "amount": 6634015211, "target": { "key": "7f7b7dbff286cd02ce2d1aab084a6ddca02628e9238735f96e204e144eeb3b2d" } } ], "extra": [ 1, 157, 28, 154, 122, 168, 121, 78, 95, 73, 132, 15, 8, 46, 174, 48, 224, 128, 68, 155, 231, 19, 142, 114, 125, 244, 26, 125, 158, 211, 74, 186, 114, 2, 17, 0, 0, 0, 1, 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