Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff115ca6fb72a0f52b5c787c4b8b6d71fbb7cc7a3a9b0360e0ab94672060a099

Tx prefix hash: 5af63db7ceb261167ce44abdf8586293447cf1c21fdf9a04d265fe7900667a3a
Tx public key: c9c7e9f970c725e928de47eff81c77524480c133ef9f5f9ef559d5026c442e7e
Timestamp: 1632956588 Timestamp [UCT]: 2021-09-29 23:03:08 Age [y:d:h:m:s]: 04:032:21:03:30
Block: 343458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1058701 RingCT/type: yes/0
Extra: 01c9c7e9f970c725e928de47eff81c77524480c133ef9f5f9ef559d5026c442e7e0211000000105410958b000000000000000000

1 output(s) for total of 44.666456425000 dcy

stealth address amount amount idx
00: 5e19e6999f340b3a472facb3d935ab5bc3121e782c8df63b40e8748cf1007916 44.666456425000 705009 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": 343468, "vin": [ { "gen": { "height": 343458 } } ], "vout": [ { "amount": 44666456425, "target": { "key": "5e19e6999f340b3a472facb3d935ab5bc3121e782c8df63b40e8748cf1007916" } } ], "extra": [ 1, 201, 199, 233, 249, 112, 199, 37, 233, 40, 222, 71, 239, 248, 28, 119, 82, 68, 128, 193, 51, 239, 159, 95, 158, 245, 89, 213, 2, 108, 68, 46, 126, 2, 17, 0, 0, 0, 16, 84, 16, 149, 139, 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