Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66839ca0522aae6a27cfaced74696699e5162ca2981ce8f3a5252d296c281078

Tx prefix hash: 98ea2c74d9fc7acd7bab3243e6b54ff324821394376ea885e2b3d1b7b0eb82c9
Tx public key: 7eacbaa6a6a0db0a4864a15c6591eb97f0c01c4c2103c0a9417a0cc6076bc513
Timestamp: 1652029422 Timestamp [UCT]: 2022-05-08 17:03:42 Age [y:d:h:m:s]: 02:243:20:13:31
Block: 496870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694617 RingCT/type: yes/0
Extra: 017eacbaa6a6a0db0a4864a15c6591eb97f0c01c4c2103c0a9417a0cc6076bc5130211000000014da16a3a000000000000000000

1 output(s) for total of 13.856822043000 dcy

stealth address amount amount idx
00: 0271f0d2fc6cde9cf30bfdfe0e9a8fa11de4563a2f95f11186108e77e407c8df 13.856822043000 920879 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": 496880, "vin": [ { "gen": { "height": 496870 } } ], "vout": [ { "amount": 13856822043, "target": { "key": "0271f0d2fc6cde9cf30bfdfe0e9a8fa11de4563a2f95f11186108e77e407c8df" } } ], "extra": [ 1, 126, 172, 186, 166, 166, 160, 219, 10, 72, 100, 161, 92, 101, 145, 235, 151, 240, 192, 28, 76, 33, 3, 192, 169, 65, 122, 12, 198, 7, 107, 197, 19, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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