Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 709bfcc1f6834e88f7bc7af74c47ab2ffb82ec360cb30e00e6d211d63b94f78a

Tx prefix hash: ae4135055c1e4e28596bd4b2eab4b362f5658cfde1fde98a9de20cf54de0607e
Tx public key: 535c30ba25741639e055c102e8d55e7a8ccfdd106be1aa440dbda23cc71b2262
Timestamp: 1699558878 Timestamp [UCT]: 2023-11-09 19:41:18 Age [y:d:h:m:s]: 01:150:19:07:02
Block: 888094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368955 RingCT/type: yes/0
Extra: 01535c30ba25741639e055c102e8d55e7a8ccfdd106be1aa440dbda23cc71b2262021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.700448022000 dcy

stealth address amount amount idx
00: 8d1a350d66d814fa23f0221ae0310891d510180c33b232b5ba79e84d96ddad34 0.700448022000 1344013 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": 888104, "vin": [ { "gen": { "height": 888094 } } ], "vout": [ { "amount": 700448022, "target": { "key": "8d1a350d66d814fa23f0221ae0310891d510180c33b232b5ba79e84d96ddad34" } } ], "extra": [ 1, 83, 92, 48, 186, 37, 116, 22, 57, 224, 85, 193, 2, 232, 213, 94, 122, 140, 207, 221, 16, 107, 225, 170, 68, 13, 189, 162, 60, 199, 27, 34, 98, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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