Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a1f2bb41a1c55cbb10e53cf1a9bd9517b47ecb3f3f5d31fc9dfad43b5b52fc

Tx prefix hash: 90a41c6c7bf8a82a12e2a8ad4a68aff7f1c5a933462a056588fe51e4b96fff4f
Tx public key: f176742645ea13e6472e46b269e12e3fba0bf909395f4ac8d8b81a052d7e4947
Timestamp: 1639041012 Timestamp [UCT]: 2021-12-09 09:10:12 Age [y:d:h:m:s]: 03:157:04:12:56
Block: 391657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 891120 RingCT/type: yes/0
Extra: 01f176742645ea13e6472e46b269e12e3fba0bf909395f4ac8d8b81a052d7e4947021100000009e59f5d07000000000000000000

1 output(s) for total of 30.922752048000 dcy

stealth address amount amount idx
00: 692d82784494af2e6e55b76a7843eb35dbb01510bf6b452ec96e372c38547fed 30.922752048000 788128 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": 391667, "vin": [ { "gen": { "height": 391657 } } ], "vout": [ { "amount": 30922752048, "target": { "key": "692d82784494af2e6e55b76a7843eb35dbb01510bf6b452ec96e372c38547fed" } } ], "extra": [ 1, 241, 118, 116, 38, 69, 234, 19, 230, 71, 46, 70, 178, 105, 225, 46, 63, 186, 11, 249, 9, 57, 95, 74, 200, 216, 184, 26, 5, 45, 126, 73, 71, 2, 17, 0, 0, 0, 9, 229, 159, 93, 7, 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