Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 293b4056ed242fc7f3b24a479fc80f55bebb814c92ccdaea1f610af0a89bfcf1

Tx prefix hash: 87aa6b9fa5ab5214ab6c073aa562caf79af01697b02b3c335e648338eb6d28a4
Tx public key: 08d7eac0a51fe53c803ff510bf10529020e473beab29ea63b7f298922b7c59e5
Timestamp: 1670091956 Timestamp [UCT]: 2022-12-03 18:25:56 Age [y:d:h:m:s]: 02:086:07:59:51
Block: 644683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 583377 RingCT/type: yes/0
Extra: 0108d7eac0a51fe53c803ff510bf10529020e473beab29ea63b7f298922b7c59e502110000000183600029000000000000000000

1 output(s) for total of 4.486395896000 dcy

stealth address amount amount idx
00: e5e3578102bcfcf796bbd79bcc6bb7afa0e58c6ae04d429ca8a8282b2a41fcbd 4.486395896000 1084750 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": 644693, "vin": [ { "gen": { "height": 644683 } } ], "vout": [ { "amount": 4486395896, "target": { "key": "e5e3578102bcfcf796bbd79bcc6bb7afa0e58c6ae04d429ca8a8282b2a41fcbd" } } ], "extra": [ 1, 8, 215, 234, 192, 165, 31, 229, 60, 128, 63, 245, 16, 191, 16, 82, 144, 32, 228, 115, 190, 171, 41, 234, 99, 183, 242, 152, 146, 43, 124, 89, 229, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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