Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c204b778ec3ae9562b76a787fdb76256928dc429d228d9720117fd3f71b4da

Tx prefix hash: 9b76863caa160b663fdea32438aaf4be5e700b72a19fefd29f283be71381e9a2
Tx public key: 71942ef909457355b6f293cd4e10235f9d9d7c214d5c73a951ef4bd9d77c2901
Timestamp: 1699819990 Timestamp [UCT]: 2023-11-12 20:13:10 Age [y:d:h:m:s]: 01:150:02:52:43
Block: 890261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368467 RingCT/type: yes/0
Extra: 0171942ef909457355b6f293cd4e10235f9d9d7c214d5c73a951ef4bd9d77c290102110000000533af99f4000000000000000000

1 output(s) for total of 0.688962747000 dcy

stealth address amount amount idx
00: b717020cc58a830377475ca5fad28ebcb0750ad6f894f3c5771622359d29b209 0.688962747000 1346284 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": 890271, "vin": [ { "gen": { "height": 890261 } } ], "vout": [ { "amount": 688962747, "target": { "key": "b717020cc58a830377475ca5fad28ebcb0750ad6f894f3c5771622359d29b209" } } ], "extra": [ 1, 113, 148, 46, 249, 9, 69, 115, 85, 182, 242, 147, 205, 78, 16, 35, 95, 157, 157, 124, 33, 77, 92, 115, 169, 81, 239, 75, 217, 215, 124, 41, 1, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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