Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 685bf588c9cd776170fc0f7e10f11e85760659bc7df841f40e537cdf9339267c

Tx prefix hash: 2ab40f428656b140c4435e6cb1953da4a6f5901988a4862823f731580c613c3c
Tx public key: be4d27a23532e6fc381e1e62f53f70f022e3d00ee0e7bd52ee29d0e5b642edc5
Timestamp: 1729067400 Timestamp [UCT]: 2024-10-16 08:30:00 Age [y:d:h:m:s]: 00:149:10:38:06
Block: 1132737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106585 RingCT/type: yes/0
Extra: 01be4d27a23532e6fc381e1e62f53f70f022e3d00ee0e7bd52ee29d0e5b642edc50211000000073cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f8d5e836b7ad3ff242a6d4359e289c195ac9c732d566a723a6f41d380d12dc9 0.600000000000 1615720 of 15

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": 1132747, "vin": [ { "gen": { "height": 1132737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f8d5e836b7ad3ff242a6d4359e289c195ac9c732d566a723a6f41d380d12dc9" } } ], "extra": [ 1, 190, 77, 39, 162, 53, 50, 230, 252, 56, 30, 30, 98, 245, 63, 112, 240, 34, 227, 208, 14, 224, 231, 189, 82, 238, 41, 208, 229, 182, 66, 237, 197, 2, 17, 0, 0, 0, 7, 60, 208, 252, 6, 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