Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a9841e096b6adc09c5b75c12d93da4ecfcb95fb16ab763ab56f2d3db918684

Tx prefix hash: 6d6234ef7db062b05f569ed7ba4d70243a2976ecc561d3e769ac947f3f409cf3
Tx public key: 3d94431b54396c347bef23219ebc744e75c33b669dac9a0156d75f0b32f21735
Timestamp: 1582966742 Timestamp [UCT]: 2020-02-29 08:59:02 Age [y:d:h:m:s]: 04:345:12:50:08
Block: 73847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140502 RingCT/type: yes/0
Extra: 013d94431b54396c347bef23219ebc744e75c33b669dac9a0156d75f0b32f21735021100000252724f989b000000000000000000

1 output(s) for total of 349.414220042000 dcy

stealth address amount amount idx
00: fa1bbb42274faa198f7b47c6e9e64dfbc95b00ce5e5f9a2794f524497bc1028b 349.414220042000 136443 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": 73857, "vin": [ { "gen": { "height": 73847 } } ], "vout": [ { "amount": 349414220042, "target": { "key": "fa1bbb42274faa198f7b47c6e9e64dfbc95b00ce5e5f9a2794f524497bc1028b" } } ], "extra": [ 1, 61, 148, 67, 27, 84, 57, 108, 52, 123, 239, 35, 33, 158, 188, 116, 78, 117, 195, 59, 102, 157, 172, 154, 1, 86, 215, 95, 11, 50, 242, 23, 53, 2, 17, 0, 0, 2, 82, 114, 79, 152, 155, 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