Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc42c177762dcc17766991cc683db7f24a84479d21c4547f0a6a49d436ca41c

Tx prefix hash: ce1ccd3c420d01665ee567e25cfa70eb9abc414550f6b46ef9c79c819c5f9bc7
Tx public key: d9669f8898f22f7da17cae4e90127320f37f7cf7b2445df4bd1a1e84b113e278
Timestamp: 1718166327 Timestamp [UCT]: 2024-06-12 04:25:27 Age [y:d:h:m:s]: 00:224:19:31:39
Block: 1042362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160835 RingCT/type: yes/0
Extra: 01d9669f8898f22f7da17cae4e90127320f37f7cf7b2445df4bd1a1e84b113e27802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0102e187862e9be79bb1d6b294e2712e5aae02b03264bf4a2b2f34ba9ed7e7a 0.600000000000 1511263 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": 1042372, "vin": [ { "gen": { "height": 1042362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0102e187862e9be79bb1d6b294e2712e5aae02b03264bf4a2b2f34ba9ed7e7a" } } ], "extra": [ 1, 217, 102, 159, 136, 152, 242, 47, 125, 161, 124, 174, 78, 144, 18, 115, 32, 243, 127, 124, 247, 178, 68, 93, 244, 189, 26, 30, 132, 177, 19, 226, 120, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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