Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df02a60ea0227197acbcc13d82f74d5b69dd73c09626dedfc5ab21ce08f63430

Tx prefix hash: 0bc28300fb9eb197b23733f9b6c04ab0f4a055c1f94f5078989ad1c983b3b47c
Tx public key: c48225ea6c36e55d50256510143b0272bc59edd77075a2dc5421b4d1fbf14424
Timestamp: 1632844040 Timestamp [UCT]: 2021-09-28 15:47:20 Age [y:d:h:m:s]: 03:095:22:05:05
Block: 342608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 845309 RingCT/type: yes/0
Extra: 01c48225ea6c36e55d50256510143b0272bc59edd77075a2dc5421b4d1fbf1442402110000006436fe6557000000000000000000

1 output(s) for total of 44.957840111000 dcy

stealth address amount amount idx
00: 827744c954e01a7f3bbbda4b9f439c6b880f6206f8bbd5ede94167c9ba63c21e 44.957840111000 703542 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": 342618, "vin": [ { "gen": { "height": 342608 } } ], "vout": [ { "amount": 44957840111, "target": { "key": "827744c954e01a7f3bbbda4b9f439c6b880f6206f8bbd5ede94167c9ba63c21e" } } ], "extra": [ 1, 196, 130, 37, 234, 108, 54, 229, 93, 80, 37, 101, 16, 20, 59, 2, 114, 188, 89, 237, 215, 112, 117, 162, 220, 84, 33, 180, 209, 251, 241, 68, 36, 2, 17, 0, 0, 0, 100, 54, 254, 101, 87, 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