Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d39f690499ff37e28d004bc06aa11c317b71b5cdbf9dfb357830912d9c0676

Tx prefix hash: cc7847053cb4f5fba8d627e7137686fc39f26a5878927d347d2c0ea257b7bb6e
Tx public key: c1712ba8279888f7b654cc06d804b74e84445d471cb777487cb390f0abbd118b
Timestamp: 1636938835 Timestamp [UCT]: 2021-11-15 01:13:55 Age [y:d:h:m:s]: 03:120:14:23:22
Block: 374488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864729 RingCT/type: yes/0
Extra: 01c1712ba8279888f7b654cc06d804b74e84445d471cb777487cb390f0abbd118b02110000000be59f5d07000000000000000000

1 output(s) for total of 35.250573445000 dcy

stealth address amount amount idx
00: 2d9dc167bc18fb71bde3a6a45557e9fd4b00cd27493b9ff0355a6b5514e96939 35.250573445000 757998 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": 374498, "vin": [ { "gen": { "height": 374488 } } ], "vout": [ { "amount": 35250573445, "target": { "key": "2d9dc167bc18fb71bde3a6a45557e9fd4b00cd27493b9ff0355a6b5514e96939" } } ], "extra": [ 1, 193, 113, 43, 168, 39, 152, 136, 247, 182, 84, 204, 6, 216, 4, 183, 78, 132, 68, 93, 71, 28, 183, 119, 72, 124, 179, 144, 240, 171, 189, 17, 139, 2, 17, 0, 0, 0, 11, 229, 159, 93, 7, 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