Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d57054a71c7e71e01dfdf5ad4a779a144350b58d61c6110d641334288c4037aa

Tx prefix hash: c4301b01b4318cbf7f9975a9331b87854230fc692f94528d7c6eaaf38963a00a
Tx public key: 4c69d14d77524e83c1369ce9586f5f93f3639f214e15aeaf8a57a62c4ea09471
Timestamp: 1671008912 Timestamp [UCT]: 2022-12-14 09:08:32 Age [y:d:h:m:s]: 02:037:05:07:22
Block: 652288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548472 RingCT/type: yes/0
Extra: 014c69d14d77524e83c1369ce9586f5f93f3639f214e15aeaf8a57a62c4ea094710211000000027e406890000000000000000000

1 output(s) for total of 4.233495101000 dcy

stealth address amount amount idx
00: d503782dfd16290bedd7063f20e424dbd47bb3d5d0eaeaed18c65433342118cd 4.233495101000 1092713 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": 652298, "vin": [ { "gen": { "height": 652288 } } ], "vout": [ { "amount": 4233495101, "target": { "key": "d503782dfd16290bedd7063f20e424dbd47bb3d5d0eaeaed18c65433342118cd" } } ], "extra": [ 1, 76, 105, 209, 77, 119, 82, 78, 131, 193, 54, 156, 233, 88, 111, 95, 147, 243, 99, 159, 33, 78, 21, 174, 175, 138, 87, 166, 44, 78, 160, 148, 113, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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