Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7c64d6eee8c2371adcfc45f7bb68f55309be75d267a9cad6bc58ca405fde8fa

Tx prefix hash: 2760a8ea9c98877bec22561363164eb90acc0955f12d3dfce206407e1ed77ec3
Tx public key: 65fc45595ace12b4104577b9456582e1e892bb5d79fdac97a5666e995cb6c4d2
Timestamp: 1577793909 Timestamp [UCT]: 2019-12-31 12:05:09 Age [y:d:h:m:s]: 05:003:03:37:13
Block: 35709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152256 RingCT/type: yes/0
Extra: 0165fc45595ace12b4104577b9456582e1e892bb5d79fdac97a5666e995cb6c4d2021100000095ac34bf9e000000000000000000

1 output(s) for total of 467.392902709000 dcy

stealth address amount amount idx
00: 3d38672cee1b2bf36b1f51be3fb55eaf0d6b101037a36d90cd6755b6d5b60e91 467.392902709000 60295 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": 35719, "vin": [ { "gen": { "height": 35709 } } ], "vout": [ { "amount": 467392902709, "target": { "key": "3d38672cee1b2bf36b1f51be3fb55eaf0d6b101037a36d90cd6755b6d5b60e91" } } ], "extra": [ 1, 101, 252, 69, 89, 90, 206, 18, 180, 16, 69, 119, 185, 69, 101, 130, 225, 232, 146, 187, 93, 121, 253, 172, 151, 165, 102, 110, 153, 92, 182, 196, 210, 2, 17, 0, 0, 0, 149, 172, 52, 191, 158, 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